Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef738f1f30cb1f19ce0f59c308d508c4c740f5efd1989260db504e31d8fc846d

Tx prefix hash: a2e4f2a5aa070e93bbf5358c027b2109b146f5065945d106d7a52a0da213c3ce
Tx public key: bbc825f0aba93a1c58abcda4a65f164a0c233ece085936980a2a8c0ce65f86f8
Timestamp: 1738334408 Timestamp [UCT]: 2025-01-31 14:40:08 Age [y:d:h:m:s]: 00:294:08:51:35
Block: 1209138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208142 RingCT/type: yes/0
Extra: 01bbc825f0aba93a1c58abcda4a65f164a0c233ece085936980a2a8c0ce65f86f8021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e664a47d5b38c10c9e048f67879802f00899f359b18680894ee707cd46dfe3 0.600000000000 1695879 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": 1209148, "vin": [ { "gen": { "height": 1209138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e664a47d5b38c10c9e048f67879802f00899f359b18680894ee707cd46dfe3" } } ], "extra": [ 1, 187, 200, 37, 240, 171, 169, 58, 28, 88, 171, 205, 164, 166, 95, 22, 74, 12, 35, 62, 206, 8, 89, 54, 152, 10, 42, 140, 12, 230, 95, 134, 248, 2, 17, 0, 0, 0, 7, 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