Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7881c06a57e16f459a15e965df94fcff23c48002b33160f16551ffa80301310

Tx prefix hash: 5ec396a41914137e73c2559938cc0d8cb2f9b0e44ffa75e5d99a7004be68023b
Tx public key: 0a314c5e929ce8c18d469d524a0a0851c09ca0ec39e2e9440673744cf2827226
Timestamp: 1590434275 Timestamp [UCT]: 2020-05-25 19:17:55 Age [y:d:h:m:s]: 04:217:21:19:09
Block: 103594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081536 RingCT/type: yes/0
Extra: 010a314c5e929ce8c18d469d524a0a0851c09ca0ec39e2e9440673744cf28272260211000003664710461d000000000000000000

1 output(s) for total of 278.452314121000 dcy

stealth address amount amount idx
00: 4b424e3e8b86fa7efdf5ef1fbcf52f5281dd59abda08484d51b5a41b99bcea0d 278.452314121000 181535 of 0

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": 103604, "vin": [ { "gen": { "height": 103594 } } ], "vout": [ { "amount": 278452314121, "target": { "key": "4b424e3e8b86fa7efdf5ef1fbcf52f5281dd59abda08484d51b5a41b99bcea0d" } } ], "extra": [ 1, 10, 49, 76, 94, 146, 156, 232, 193, 141, 70, 157, 82, 74, 10, 8, 81, 192, 156, 160, 236, 57, 226, 233, 68, 6, 115, 116, 76, 242, 130, 114, 38, 2, 17, 0, 0, 3, 102, 71, 16, 70, 29, 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