Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe8e1bf77234e90b732ffd628b2da220cee58bf0043664418b5edbddd89f393

Tx prefix hash: 903a4552540d2d1017d9e4abc454493a0e6e69699fb940fcb8c301cd59e96f09
Tx public key: d243e09d08f90d0c30e7fd9fb521414cfd71807e968086e219966b45fc079295
Timestamp: 1716903600 Timestamp [UCT]: 2024-05-28 13:40:00 Age [y:d:h:m:s]: 00:353:18:22:08
Block: 1031896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252854 RingCT/type: yes/0
Extra: 01d243e09d08f90d0c30e7fd9fb521414cfd71807e968086e219966b45fc0792950211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 556531643d907a9c4d06b8dfaf81139df20712eabd523503769b2f07867db9e0 0.600000000000 1500345 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": 1031906, "vin": [ { "gen": { "height": 1031896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556531643d907a9c4d06b8dfaf81139df20712eabd523503769b2f07867db9e0" } } ], "extra": [ 1, 210, 67, 224, 157, 8, 249, 13, 12, 48, 231, 253, 159, 181, 33, 65, 76, 253, 113, 128, 126, 150, 128, 134, 226, 25, 150, 107, 69, 252, 7, 146, 149, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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