Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c727ee53a3f3a6be056506456150e195fcc3806dd35c22058a190f958596b3cf

Tx prefix hash: 881758f8ba49215dab72631f195321fb33e5da5d98cf962ad0490cfa4b8d6514
Tx public key: ebcba83fdcbd55c4fae6426bdf3acdc989967fb4b253c54ed9d0ca8d6f2c7480
Timestamp: 1746309047 Timestamp [UCT]: 2025-05-03 21:50:47 Age [y:d:h:m:s]: 00:201:00:37:12
Block: 1275149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141381 RingCT/type: yes/0
Extra: 01ebcba83fdcbd55c4fae6426bdf3acdc989967fb4b253c54ed9d0ca8d6f2c74800211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94425639ca6b80a089be296130e9f4d03e7f882c094d1ae329007b56eff0cc56 0.600000000000 1762454 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": 1275159, "vin": [ { "gen": { "height": 1275149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94425639ca6b80a089be296130e9f4d03e7f882c094d1ae329007b56eff0cc56" } } ], "extra": [ 1, 235, 203, 168, 63, 220, 189, 85, 196, 250, 230, 66, 107, 223, 58, 205, 201, 137, 150, 127, 180, 178, 83, 197, 78, 217, 208, 202, 141, 111, 44, 116, 128, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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