Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750d4bd9066a96b1f4b3d3f38b4560f7d55d1ba4e3858b76ccbed7ba114bd798

Tx prefix hash: a48f8ba680cbcd0c54d77150079a61a4a246c8cc5ca2899351a1f0a630319913
Tx public key: eac4b636f23c693db0b3f518ac7b40b73319526779e00c77bcf3dfe2774f7cfb
Timestamp: 1730784205 Timestamp [UCT]: 2024-11-05 05:23:25 Age [y:d:h:m:s]: 00:130:02:47:03
Block: 1146871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92843 RingCT/type: yes/0
Extra: 01eac4b636f23c693db0b3f518ac7b40b73319526779e00c77bcf3dfe2774f7cfb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37fc95f201cd898dabb3991c8533782095ccac4d348ea4eb624f8ef091a8cf5b 0.600000000000 1631562 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": 1146881, "vin": [ { "gen": { "height": 1146871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37fc95f201cd898dabb3991c8533782095ccac4d348ea4eb624f8ef091a8cf5b" } } ], "extra": [ 1, 234, 196, 182, 54, 242, 60, 105, 61, 176, 179, 245, 24, 172, 123, 64, 183, 51, 25, 82, 103, 121, 224, 12, 119, 188, 243, 223, 226, 119, 79, 124, 251, 2, 17, 0, 0, 0, 3, 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