Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eb0d8e4aeeffddd90c5b25a6cdb791c6881a6f6da04906f96dc2a37a34be531

Tx prefix hash: 670136ab4042f34dfe7a6581ec898faf7b55e261d8f0d8edf640f008631063d1
Tx public key: f3e16685c84e99110c490af5170996a7d222c536ccb59da2d3cf106cd38a6fbb
Timestamp: 1580267594 Timestamp [UCT]: 2020-01-29 03:13:14 Age [y:d:h:m:s]: 04:308:22:39:44
Block: 54707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111387 RingCT/type: yes/0
Extra: 01f3e16685c84e99110c490af5170996a7d222c536ccb59da2d3cf106cd38a6fbb0211000000312264afe6000000000000000000

1 output(s) for total of 404.328007033000 dcy

stealth address amount amount idx
00: 3fe364a46bef1adfce857a0c33c238d678d1e26a954e83196095d4ca88ca52ee 404.328007033000 101170 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": 54717, "vin": [ { "gen": { "height": 54707 } } ], "vout": [ { "amount": 404328007033, "target": { "key": "3fe364a46bef1adfce857a0c33c238d678d1e26a954e83196095d4ca88ca52ee" } } ], "extra": [ 1, 243, 225, 102, 133, 200, 78, 153, 17, 12, 73, 10, 245, 23, 9, 150, 167, 210, 34, 197, 54, 204, 181, 157, 162, 211, 207, 16, 108, 211, 138, 111, 187, 2, 17, 0, 0, 0, 49, 34, 100, 175, 230, 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