Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28258c57015d37d54658fe3bd93b801385c41b1d5ffb61d128db71a60d5f8259

Tx prefix hash: 52a09b9d77810e76cbcf4650888fc79418c164f41fd35c22740e86ec2985433f
Tx public key: e971c0f618c60d62e6d24ae77341f12ebe70e105046f7548b759d2ada9c0bd9b
Timestamp: 1711560820 Timestamp [UCT]: 2024-03-27 17:33:40 Age [y:d:h:m:s]: 00:293:09:45:26
Block: 987608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209999 RingCT/type: yes/0
Extra: 01e971c0f618c60d62e6d24ae77341f12ebe70e105046f7548b759d2ada9c0bd9b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40fe0373066143563e8176ea8a7248df6eb060a82d4b3eb7744f9a94624f7f18 0.600000000000 1447861 of 15

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": 987618, "vin": [ { "gen": { "height": 987608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40fe0373066143563e8176ea8a7248df6eb060a82d4b3eb7744f9a94624f7f18" } } ], "extra": [ 1, 233, 113, 192, 246, 24, 198, 13, 98, 230, 210, 74, 231, 115, 65, 241, 46, 190, 112, 225, 5, 4, 111, 117, 72, 183, 89, 210, 173, 169, 192, 189, 155, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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