Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c41259c315c6cf2727ba0fb2886b501efe97978b0719fee920ebe3cdff330f94

Tx prefix hash: e1c468aaa3f96c5fc27317583b8bbe872a8242dc4891e56a3449cec4bc5a24cc
Tx public key: 40a89302ce6c440404c0e05c51832c41a0cf364ef2059e57b314c440ee8b46e8
Timestamp: 1746065871 Timestamp [UCT]: 2025-05-01 02:17:51 Age [y:d:h:m:s]: 00:204:12:45:35
Block: 1273124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143896 RingCT/type: yes/0
Extra: 0140a89302ce6c440404c0e05c51832c41a0cf364ef2059e57b314c440ee8b46e8021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8b41d8bb82311cf7986ac9bf98e7beaf43e4a1ebacb63af5175395dbb98c523 0.600000000000 1760405 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1273134, "vin": [ { "gen": { "height": 1273124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8b41d8bb82311cf7986ac9bf98e7beaf43e4a1ebacb63af5175395dbb98c523" } } ], "extra": [ 1, 64, 168, 147, 2, 206, 108, 68, 4, 4, 192, 224, 92, 81, 131, 44, 65, 160, 207, 54, 78, 242, 5, 158, 87, 179, 20, 196, 64, 238, 139, 70, 232, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8