Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e1def96e9b2da35156f103b6b9fb3d99d0a6756c252bca80084a10a69c33733

Tx prefix hash: 6737b2157bb41893f5ac16477b394c8b0047bc8f1d3eb0bb4dd33b63be23416b
Tx public key: 8b029988b0c4cf69183ebf4736523d3a729237a8e467d84ed7f37c036da33c07
Timestamp: 1741242958 Timestamp [UCT]: 2025-03-06 06:35:58 Age [y:d:h:m:s]: 00:259:21:26:19
Block: 1233211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183479 RingCT/type: yes/0
Extra: 018b029988b0c4cf69183ebf4736523d3a729237a8e467d84ed7f37c036da33c07021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4120cd233a2f3750dd6bc1b7ac37c7b084c85d321f88ef4d9ebe4465b07cd8b5 0.600000000000 1720130 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": 1233221, "vin": [ { "gen": { "height": 1233211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4120cd233a2f3750dd6bc1b7ac37c7b084c85d321f88ef4d9ebe4465b07cd8b5" } } ], "extra": [ 1, 139, 2, 153, 136, 176, 196, 207, 105, 24, 62, 191, 71, 54, 82, 61, 58, 114, 146, 55, 168, 228, 103, 216, 78, 215, 243, 124, 3, 109, 163, 60, 7, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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