Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce5d84ab6cf05e9a4c144f15ab81d8c7aab18e3c4302ff7d4dbc090e9c4811df

Tx prefix hash: 4b71b4526b11d003158317667c4499597bebfd789f0ec449b3190520fb677e06
Tx public key: 28b1e665baaccb5136e425d9a186c8e046edfa9e0a0e1ad73fa6edd475e5e195
Timestamp: 1735414905 Timestamp [UCT]: 2024-12-28 19:41:45 Age [y:d:h:m:s]: 00:314:06:06:29
Block: 1185217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222113 RingCT/type: yes/0
Extra: 0128b1e665baaccb5136e425d9a186c8e046edfa9e0a0e1ad73fa6edd475e5e1950211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69319b105ad2d810f3cd7823af1879a535c30bbdf8089118ab1feba77e6964c3 0.600000000000 1671684 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": 1185227, "vin": [ { "gen": { "height": 1185217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69319b105ad2d810f3cd7823af1879a535c30bbdf8089118ab1feba77e6964c3" } } ], "extra": [ 1, 40, 177, 230, 101, 186, 172, 203, 81, 54, 228, 37, 217, 161, 134, 200, 224, 70, 237, 250, 158, 10, 14, 26, 215, 63, 166, 237, 212, 117, 229, 225, 149, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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