Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7316c7c3f7d26b4903d8c04842d3cbe27b1cc51bad8a5f3ee7878f15d452ce75

Tx prefix hash: a76f363ff280334df33dfe6247c8e3a6d5f1b01e26ab2a667bfa46bddae443ec
Tx public key: 45b3fa4ce279e0815a0cfea309ab059db3ebe540d52d8b77e641b86660688572
Timestamp: 1578899962 Timestamp [UCT]: 2020-01-13 07:19:22 Age [y:d:h:m:s]: 05:003:00:32:50
Block: 44427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152600 RingCT/type: yes/0
Extra: 0145b3fa4ce279e0815a0cfea309ab059db3ebe540d52d8b77e641b86660688572021100000009d81c26c0000000000000000000

1 output(s) for total of 437.366093182000 dcy

stealth address amount amount idx
00: 8a9b7c3f52366fd1b3de61cb2d66d4eafb579047118810c3dc5f6473a18abe67 437.366093182000 80837 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": 44437, "vin": [ { "gen": { "height": 44427 } } ], "vout": [ { "amount": 437366093182, "target": { "key": "8a9b7c3f52366fd1b3de61cb2d66d4eafb579047118810c3dc5f6473a18abe67" } } ], "extra": [ 1, 69, 179, 250, 76, 226, 121, 224, 129, 90, 12, 254, 163, 9, 171, 5, 157, 179, 235, 229, 64, 213, 45, 139, 119, 230, 65, 184, 102, 96, 104, 133, 114, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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