Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef4b85a06d0894df81736cc3eb07e559f1e884d3f7aef35aff40d7a74697acb4

Tx prefix hash: bdb88bda2121ba7b7c5d09a185032cce7ee8d24f3420d295bb8d08b2bd5833a3
Tx public key: 3b7b88d9e6f04008f923e7e812a48a4bf84bf7cb0bbfb1dad01755dea0bd19fd
Timestamp: 1657258627 Timestamp [UCT]: 2022-07-08 05:37:07 Age [y:d:h:m:s]: 02:255:08:19:57
Block: 539107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703643 RingCT/type: yes/0
Extra: 013b7b88d9e6f04008f923e7e812a48a4bf84bf7cb0bbfb1dad01755dea0bd19fd021100000019bf7ee4e7000000000000000000

1 output(s) for total of 10.039564247000 dcy

stealth address amount amount idx
00: f9d646e74d153088fe3d47ac63cfd961b80141499414c2e03577a7d954e648be 10.039564247000 969178 of 0

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": 539117, "vin": [ { "gen": { "height": 539107 } } ], "vout": [ { "amount": 10039564247, "target": { "key": "f9d646e74d153088fe3d47ac63cfd961b80141499414c2e03577a7d954e648be" } } ], "extra": [ 1, 59, 123, 136, 217, 230, 240, 64, 8, 249, 35, 231, 232, 18, 164, 138, 75, 248, 75, 247, 203, 11, 191, 177, 218, 208, 23, 85, 222, 160, 189, 25, 253, 2, 17, 0, 0, 0, 25, 191, 126, 228, 231, 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