Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17e3f0d29a0e8af41754072ecb92ed9d35900e89cc6ef4b4664de44e2a7d3f3

Tx prefix hash: 509fdd2cca2893c12f1cf2b0af19a8906ea9f52768f579090963f9065f295872
Tx public key: 70eac35dcc3a76667ab8d39311d9e798f267e2fafd3a7afc7dd999588ef09405
Timestamp: 1751170812 Timestamp [UCT]: 2025-06-29 04:20:12 Age [y:d:h:m:s]: 00:189:06:26:42
Block: 1314964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133465 RingCT/type: yes/0
Extra: 0170eac35dcc3a76667ab8d39311d9e798f267e2fafd3a7afc7dd999588ef09405021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 760da84c08c5b7fe22e5ff3b02168e6eca51c6dc01e588cb1fb659a1f2024a86 0.600000000000 1802617 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": 1314974, "vin": [ { "gen": { "height": 1314964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "760da84c08c5b7fe22e5ff3b02168e6eca51c6dc01e588cb1fb659a1f2024a86" } } ], "extra": [ 1, 112, 234, 195, 93, 204, 58, 118, 102, 122, 184, 211, 147, 17, 217, 231, 152, 242, 103, 226, 250, 253, 58, 122, 252, 125, 217, 153, 88, 142, 240, 148, 5, 2, 17, 0, 0, 0, 2, 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