Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 427de9b41d28d78e9d6b8fffa5b741025b0a98556f4a2ba5553ed585fd534c79

Tx prefix hash: fbe4092ee3a1152699ff2d2e796ab6178594187121faeb0089bcea1702a9884b
Tx public key: bb2dfe463aff059a7a5ebc52e9e52b649cbdfd2571e890ce5e6a8a761cba788d
Timestamp: 1731907745 Timestamp [UCT]: 2024-11-18 05:29:05 Age [y:d:h:m:s]: 00:165:06:46:53
Block: 1156182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117962 RingCT/type: yes/0
Extra: 01bb2dfe463aff059a7a5ebc52e9e52b649cbdfd2571e890ce5e6a8a761cba788d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14ffed70a3803abb1cdfe92258f9f579d62cc631d54f7cfd75a0e82a99f50eb 0.600000000000 1641805 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": 1156192, "vin": [ { "gen": { "height": 1156182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14ffed70a3803abb1cdfe92258f9f579d62cc631d54f7cfd75a0e82a99f50eb" } } ], "extra": [ 1, 187, 45, 254, 70, 58, 255, 5, 154, 122, 94, 188, 82, 233, 229, 43, 100, 156, 189, 253, 37, 113, 232, 144, 206, 94, 106, 138, 118, 28, 186, 120, 141, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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