Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d90d1f35df1d569fe3d01bd4d46cb4906051b924f0d1dd7120ceb58fcb1373e

Tx prefix hash: 160fbd40dc3d957bfdab87c1f1aabe713c1bcc0d691f280ccf5624bc4d073c2d
Tx public key: b7dc792a6c7363f66dbf063f98c705229253b88e1c46cb550d4ae58a153e5dda
Timestamp: 1634963554 Timestamp [UCT]: 2021-10-23 04:32:34 Age [y:d:h:m:s]: 03:190:09:13:23
Block: 358572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914188 RingCT/type: yes/0
Extra: 01b7dc792a6c7363f66dbf063f98c705229253b88e1c46cb550d4ae58a153e5dda0211000000018d0de867000000000000000000

1 output(s) for total of 39.801782736000 dcy

stealth address amount amount idx
00: 4f9a7f1eb3c8789ba2d2831ad4a4c7c2c013966213d9a3be1e166eb466fcbf17 39.801782736000 730569 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": 358582, "vin": [ { "gen": { "height": 358572 } } ], "vout": [ { "amount": 39801782736, "target": { "key": "4f9a7f1eb3c8789ba2d2831ad4a4c7c2c013966213d9a3be1e166eb466fcbf17" } } ], "extra": [ 1, 183, 220, 121, 42, 108, 115, 99, 246, 109, 191, 6, 63, 152, 199, 5, 34, 146, 83, 184, 142, 28, 70, 203, 85, 13, 74, 229, 138, 21, 62, 93, 218, 2, 17, 0, 0, 0, 1, 141, 13, 232, 103, 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