Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b10f043cb7e7a0200e63c3e338ad4fcd3b7af239fbe96ea9a37f5899cb07db0

Tx prefix hash: 563d2bd0a4d2e419051a0a8be952a749f6eae46a931c805e2a40e8ce376a9f8d
Tx public key: e5ddfb55df1536032e79ef41b5725a0ed1b1625268073542d44f8ce08179d8b2
Timestamp: 1659337823 Timestamp [UCT]: 2022-08-01 07:10:23 Age [y:d:h:m:s]: 02:247:02:07:53
Block: 556229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697801 RingCT/type: yes/0
Extra: 01e5ddfb55df1536032e79ef41b5725a0ed1b1625268073542d44f8ce08179d8b20211000000166570b1ef000000000000000000

1 output(s) for total of 8.810134619000 dcy

stealth address amount amount idx
00: da81e06bd8776f423c8a5fada2a9f5701b907e3aa644a480b15a8bd2e1e4a018 8.810134619000 988157 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": 556239, "vin": [ { "gen": { "height": 556229 } } ], "vout": [ { "amount": 8810134619, "target": { "key": "da81e06bd8776f423c8a5fada2a9f5701b907e3aa644a480b15a8bd2e1e4a018" } } ], "extra": [ 1, 229, 221, 251, 85, 223, 21, 54, 3, 46, 121, 239, 65, 181, 114, 90, 14, 209, 177, 98, 82, 104, 7, 53, 66, 212, 79, 140, 224, 129, 121, 216, 178, 2, 17, 0, 0, 0, 22, 101, 112, 177, 239, 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