Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549f70f38722bbd19c67d2f9333e21ca5fdf5eb2c95ec532b960e1a59379a9c6

Tx prefix hash: 39c230290668d6cf099b5f7f07435ecbd6abafed4e45ed0d6af1922535c5ed4e
Tx public key: 5bbf6f4ccec64f9cb99481478c09f6aa33204bc329d692062f8a903bbef5b48a
Timestamp: 1645472480 Timestamp [UCT]: 2022-02-21 19:41:20 Age [y:d:h:m:s]: 02:280:09:09:58
Block: 443544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719778 RingCT/type: yes/0
Extra: 015bbf6f4ccec64f9cb99481478c09f6aa33204bc329d692062f8a903bbef5b48a021100000016c9067537000000000000000000

1 output(s) for total of 20.813968471000 dcy

stealth address amount amount idx
00: 1841394e596dbec9ef8435bb9bbe675ba58bd1a81af6b1bbec54c363e6f864c3 20.813968471000 856605 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": 443554, "vin": [ { "gen": { "height": 443544 } } ], "vout": [ { "amount": 20813968471, "target": { "key": "1841394e596dbec9ef8435bb9bbe675ba58bd1a81af6b1bbec54c363e6f864c3" } } ], "extra": [ 1, 91, 191, 111, 76, 206, 198, 79, 156, 185, 148, 129, 71, 140, 9, 246, 170, 51, 32, 75, 195, 41, 214, 146, 6, 47, 138, 144, 59, 190, 245, 180, 138, 2, 17, 0, 0, 0, 22, 201, 6, 117, 55, 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