Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2706eb7d86c403c6576430669a067889a6ba93c99466869286c397dc4c62479a

Tx prefix hash: 311fe6e3ebb926df79d9852cd7878c12164ac4866a7a5c320d6fe81cac1ee59c
Tx public key: 500ac3229d2d8914d3e32d1544bbb87f4f6b44545af5f157779703e3b372cfe2
Timestamp: 1673168009 Timestamp [UCT]: 2023-01-08 08:53:29 Age [y:d:h:m:s]: 03:000:07:22:35
Block: 670153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 780574 RingCT/type: yes/0
Extra: 01500ac3229d2d8914d3e32d1544bbb87f4f6b44545af5f157779703e3b372cfe20211000000098b7b6602000000000000000000

1 output(s) for total of 3.694067903000 dcy

stealth address amount amount idx
00: 66c58f68954fdcd1f7f2f48c4f6ac34c047da255b1e249e87c6799f450bf2d3f 3.694067903000 1111528 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": 670163, "vin": [ { "gen": { "height": 670153 } } ], "vout": [ { "amount": 3694067903, "target": { "key": "66c58f68954fdcd1f7f2f48c4f6ac34c047da255b1e249e87c6799f450bf2d3f" } } ], "extra": [ 1, 80, 10, 195, 34, 157, 45, 137, 20, 211, 227, 45, 21, 68, 187, 184, 127, 79, 107, 68, 84, 90, 245, 241, 87, 119, 151, 3, 227, 179, 114, 207, 226, 2, 17, 0, 0, 0, 9, 139, 123, 102, 2, 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