Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26d1ac41876b9c6db0bd0fd265ae1b34cabfb5c337f2f8b4413d1f6f175ab419

Tx prefix hash: f7b3796bc5f6cfb4d49a50a50e1f82db52587b739dc42395c67cf6d91d88fec3
Tx public key: 8c4cca46ae007645a43543852f31a8d2f142fe92dc94cdf64d8c94a0341277c8
Timestamp: 1713534008 Timestamp [UCT]: 2024-04-19 13:40:08 Age [y:d:h:m:s]: 00:225:21:21:14
Block: 1003946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161713 RingCT/type: yes/0
Extra: 018c4cca46ae007645a43543852f31a8d2f142fe92dc94cdf64d8c94a0341277c8021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a47f1cd4452e3e8cf2fd4701450213f7da913209981ce0b86784016aefab76c2 0.600000000000 1464502 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": 1003956, "vin": [ { "gen": { "height": 1003946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a47f1cd4452e3e8cf2fd4701450213f7da913209981ce0b86784016aefab76c2" } } ], "extra": [ 1, 140, 76, 202, 70, 174, 0, 118, 69, 164, 53, 67, 133, 47, 49, 168, 210, 241, 66, 254, 146, 220, 148, 205, 246, 77, 140, 148, 160, 52, 18, 119, 200, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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