Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 690e5964d54524928f2c4d628807cd279c7edbc2c8fe0d8d103149cbf6c3af74

Tx prefix hash: 23fed9b3042d379d84258d5ef681203247bc7bce96f3e55e0d8ecb8b1c89ca55
Tx public key: 8d0e51818a46adc32619f2f851048f9d4191465d7191754ee2f14435956e1145
Timestamp: 1677490493 Timestamp [UCT]: 2023-02-27 09:34:53 Age [y:d:h:m:s]: 02:033:15:29:39
Block: 706005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545630 RingCT/type: yes/0
Extra: 018d0e51818a46adc32619f2f851048f9d4191465d7191754ee2f14435956e114502110000000183600029000000000000000000

1 output(s) for total of 2.810038453000 dcy

stealth address amount amount idx
00: 289c5b0ae4c4181c8eb66d5b81ba4e59564e0fcf67c5e32293dce50a117eac08 2.810038453000 1149722 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": 706015, "vin": [ { "gen": { "height": 706005 } } ], "vout": [ { "amount": 2810038453, "target": { "key": "289c5b0ae4c4181c8eb66d5b81ba4e59564e0fcf67c5e32293dce50a117eac08" } } ], "extra": [ 1, 141, 14, 81, 129, 138, 70, 173, 195, 38, 25, 242, 248, 81, 4, 143, 157, 65, 145, 70, 93, 113, 145, 117, 78, 226, 241, 68, 53, 149, 110, 17, 69, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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