Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f972d02d918ddd967444b9c66890a7339a7be232eaac58554c911f2163e9d8

Tx prefix hash: 269858870ff753f15e13318de68dc884008230aa25961c2e33a0cad2a666b981
Tx public key: 9f91d8a9c5d80b95eb0d96611e95e834ba1dca7270e4bf73bb843577e2943b9b
Timestamp: 1578727642 Timestamp [UCT]: 2020-01-11 07:27:22 Age [y:d:h:m:s]: 05:030:06:25:32
Block: 43129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171707 RingCT/type: yes/0
Extra: 019f91d8a9c5d80b95eb0d96611e95e834ba1dca7270e4bf73bb843577e2943b9b021100000006d81c26c0000000000000000000

1 output(s) for total of 441.668638379000 dcy

stealth address amount amount idx
00: 3b93929ec2985b7bd395b1262103d09d7c57f7b73e9618f98fdaa63c98926780 441.668638379000 77972 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": 43139, "vin": [ { "gen": { "height": 43129 } } ], "vout": [ { "amount": 441668638379, "target": { "key": "3b93929ec2985b7bd395b1262103d09d7c57f7b73e9618f98fdaa63c98926780" } } ], "extra": [ 1, 159, 145, 216, 169, 197, 216, 11, 149, 235, 13, 150, 97, 30, 149, 232, 52, 186, 29, 202, 114, 112, 228, 191, 115, 187, 132, 53, 119, 226, 148, 59, 155, 2, 17, 0, 0, 0, 6, 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