Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c9c050199bf9109baad333922bf567c69c9d8942baa4871bc4694f4d0224b0

Tx prefix hash: 03bb29eae097f05e7e0e558dd385f8d38461479ac524d6dffa145435904688b0
Tx public key: b10befa9982f33df48a9ae24d59a208b415e0080eaa5cb8c7983c11fa0e77af2
Timestamp: 1732495309 Timestamp [UCT]: 2024-11-25 00:41:49 Age [y:d:h:m:s]: 00:124:09:47:16
Block: 1161052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88721 RingCT/type: yes/0
Extra: 01b10befa9982f33df48a9ae24d59a208b415e0080eaa5cb8c7983c11fa0e77af20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e8b981111b1797f4bf35c88d30c68c5e173da8bea26983209d9f15913f71abc 0.600000000000 1646703 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": 1161062, "vin": [ { "gen": { "height": 1161052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e8b981111b1797f4bf35c88d30c68c5e173da8bea26983209d9f15913f71abc" } } ], "extra": [ 1, 177, 11, 239, 169, 152, 47, 51, 223, 72, 169, 174, 36, 213, 154, 32, 139, 65, 94, 0, 128, 234, 165, 203, 140, 121, 131, 193, 31, 160, 231, 122, 242, 2, 17, 0, 0, 0, 6, 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