Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4112c723e835ac8ef44ff3e512955bccdda644247c6c4fb0eb685aac088744e

Tx prefix hash: 5918316e8f14da3f8287ba7b7f32d0e57cbce3bd10b2d4f94bfa144a5dcf13f5
Tx public key: cde7f356f43ffff692d399fdeb6dc0bdd08d87f1621b65404bfd9fb4268eeff0
Timestamp: 1736127207 Timestamp [UCT]: 2025-01-06 01:33:27 Age [y:d:h:m:s]: 00:073:23:03:55
Block: 1191130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52643 RingCT/type: yes/0
Extra: 01cde7f356f43ffff692d399fdeb6dc0bdd08d87f1621b65404bfd9fb4268eeff002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 074732e8a213925a5030412c4e832ff70367f43670e72e550208ea8d89748d83 0.600000000000 1677653 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": 1191140, "vin": [ { "gen": { "height": 1191130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "074732e8a213925a5030412c4e832ff70367f43670e72e550208ea8d89748d83" } } ], "extra": [ 1, 205, 231, 243, 86, 244, 63, 255, 246, 146, 211, 153, 253, 235, 109, 192, 189, 208, 141, 135, 241, 98, 27, 101, 64, 75, 253, 159, 180, 38, 142, 239, 240, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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