Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997c80e50ed5065d10d4bd2f44b2bde7a8e7dc72c1fcdaba94db156fcff44d61

Tx prefix hash: 3cb5e6c0a45dd37ddb5c91b461cb108b623968911b889d34749e278077c872ce
Tx public key: 1748efa149d434b61fea0d74d3bfc98109c6f5e02c19b9bc5d2ac448454d3dc2
Timestamp: 1751487658 Timestamp [UCT]: 2025-07-02 20:20:58 Age [y:d:h:m:s]: 00:130:01:44:17
Block: 1317459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91198 RingCT/type: yes/0
Extra: 011748efa149d434b61fea0d74d3bfc98109c6f5e02c19b9bc5d2ac448454d3dc20211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f707c6e080bf541a93ebdab5abad3ef1e845f6f3f70001ef25f3c52fc5ae1554 0.600000000000 1805126 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": 1317469, "vin": [ { "gen": { "height": 1317459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f707c6e080bf541a93ebdab5abad3ef1e845f6f3f70001ef25f3c52fc5ae1554" } } ], "extra": [ 1, 23, 72, 239, 161, 73, 212, 52, 182, 31, 234, 13, 116, 211, 191, 201, 129, 9, 198, 245, 224, 44, 25, 185, 188, 93, 42, 196, 72, 69, 77, 61, 194, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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