Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a5eee535c3d473d06e6dbc23a70dd1b4d7b1ea296180ff8315310ba766baa90

Tx prefix hash: 8ad62d4926c2430435e659d82607913b3a7f478a9d0fb078b80c42c89f6da243
Tx public key: 4344e2cfde9633c68f80840712018fdd618b3dd1b8714738427ee03f26b0a0c8
Timestamp: 1728744117 Timestamp [UCT]: 2024-10-12 14:41:57 Age [y:d:h:m:s]: 00:176:12:41:20
Block: 1130046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125938 RingCT/type: yes/0
Extra: 014344e2cfde9633c68f80840712018fdd618b3dd1b8714738427ee03f26b0a0c802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 433a8c8d9f415c6ca1f8661b1ade079478c9b8478f9c2cbd72bd1937d718600e 0.600000000000 1612917 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": 1130056, "vin": [ { "gen": { "height": 1130046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "433a8c8d9f415c6ca1f8661b1ade079478c9b8478f9c2cbd72bd1937d718600e" } } ], "extra": [ 1, 67, 68, 226, 207, 222, 150, 51, 198, 143, 128, 132, 7, 18, 1, 143, 221, 97, 139, 61, 209, 184, 113, 71, 56, 66, 126, 224, 63, 38, 176, 160, 200, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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