Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf0f5f89b451163752d273054b0e23e04e731c889903aa0935a602bdf0a7a01

Tx prefix hash: 004d82cede473d5554120187557238ab556a6867613427157429ed4abd6bf4aa
Tx public key: 99b1f8d191e936fd709abb3f644f593225d92c4a827006de074f132e2db3597c
Timestamp: 1619822879 Timestamp [UCT]: 2021-04-30 22:47:59 Age [y:d:h:m:s]: 04:010:18:51:12
Block: 251288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1028738 RingCT/type: yes/0
Extra: 0199b1f8d191e936fd709abb3f644f593225d92c4a827006de074f132e2db3597c02110000000a9c1fbdcc000000000000000000

1 output(s) for total of 90.237406911000 dcy

stealth address amount amount idx
00: 38518f9a00f76dd13f4dd049b35add29fdc41cafff38628217842fe63f05ae04 90.237406911000 527142 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": 251298, "vin": [ { "gen": { "height": 251288 } } ], "vout": [ { "amount": 90237406911, "target": { "key": "38518f9a00f76dd13f4dd049b35add29fdc41cafff38628217842fe63f05ae04" } } ], "extra": [ 1, 153, 177, 248, 209, 145, 233, 54, 253, 112, 154, 187, 63, 100, 79, 89, 50, 37, 217, 44, 74, 130, 112, 6, 222, 7, 79, 19, 46, 45, 179, 89, 124, 2, 17, 0, 0, 0, 10, 156, 31, 189, 204, 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