Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b728e09f52eb6224e4c9c3381f01a18920bc346c159f6eeff57bb6f0a70d72e

Tx prefix hash: 68d5679a0a136af3a4f7426afed51ed0237255ca27f8579b05505bd50a029ed6
Tx public key: 00ea1f59bc7c7ae7063a4b079dbc9542b4f066d6515d915db57d4467518ce7ff
Timestamp: 1735946858 Timestamp [UCT]: 2025-01-03 23:27:38 Age [y:d:h:m:s]: 00:098:16:26:19
Block: 1189635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70315 RingCT/type: yes/0
Extra: 0100ea1f59bc7c7ae7063a4b079dbc9542b4f066d6515d915db57d4467518ce7ff021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e3a49c7f1044917e6763d96a5fa83695d594975568c574ea073f37fc5d435e6 0.600000000000 1676146 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": 1189645, "vin": [ { "gen": { "height": 1189635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e3a49c7f1044917e6763d96a5fa83695d594975568c574ea073f37fc5d435e6" } } ], "extra": [ 1, 0, 234, 31, 89, 188, 124, 122, 231, 6, 58, 75, 7, 157, 188, 149, 66, 180, 240, 102, 214, 81, 93, 145, 93, 181, 125, 68, 103, 81, 140, 231, 255, 2, 17, 0, 0, 0, 9, 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