Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d75632f112b16b2dcde20629d3c1dff60aeb83c87d1fbaa0faeb81d2f2b800

Tx prefix hash: 934e862a3e80469ddf3d81f7f7880ba718111d912e26e4bde093229c467d3034
Tx public key: a6b7a0a458ffe2c21f7398f36287e5397b9998efc5a2de72a8fbd73aba002f98
Timestamp: 1737444226 Timestamp [UCT]: 2025-01-21 07:23:46 Age [y:d:h:m:s]: 00:146:21:13:28
Block: 1201985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104723 RingCT/type: yes/0
Extra: 01a6b7a0a458ffe2c21f7398f36287e5397b9998efc5a2de72a8fbd73aba002f98021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b11a21b54a1ac4cddd5477eded3d8e6ead0eeb201700a443925f7461ed4ac9ce 0.600000000000 1688644 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": 1201995, "vin": [ { "gen": { "height": 1201985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b11a21b54a1ac4cddd5477eded3d8e6ead0eeb201700a443925f7461ed4ac9ce" } } ], "extra": [ 1, 166, 183, 160, 164, 88, 255, 226, 194, 31, 115, 152, 243, 98, 135, 229, 57, 123, 153, 152, 239, 197, 162, 222, 114, 168, 251, 215, 58, 186, 0, 47, 152, 2, 17, 0, 0, 0, 2, 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