Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a310d0a4cf11ea77fc526fe571a5cacc4ac7ed0d66f9eac7e7be311566b3fc79

Tx prefix hash: 2c3142e8df389402022f375d0f76318458417832af0c1ea86ba5727883fa6a47
Tx public key: e816008d7eb24f0d41a92f3507231cbf5a571135e7246f03de3d4d128af2cbae
Timestamp: 1672506766 Timestamp [UCT]: 2022-12-31 17:12:46 Age [y:d:h:m:s]: 02:312:09:06:55
Block: 664678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742667 RingCT/type: yes/0
Extra: 01e816008d7eb24f0d41a92f3507231cbf5a571135e7246f03de3d4d128af2cbae02110000000675e3f0e9000000000000000000

1 output(s) for total of 3.851641257000 dcy

stealth address amount amount idx
00: d633d4d60d16b8eed17fa6b32d789c8c6c9c75184e01be1163a8945dd8e5ff20 3.851641257000 1105683 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": 664688, "vin": [ { "gen": { "height": 664678 } } ], "vout": [ { "amount": 3851641257, "target": { "key": "d633d4d60d16b8eed17fa6b32d789c8c6c9c75184e01be1163a8945dd8e5ff20" } } ], "extra": [ 1, 232, 22, 0, 141, 126, 178, 79, 13, 65, 169, 47, 53, 7, 35, 28, 191, 90, 87, 17, 53, 231, 36, 111, 3, 222, 61, 77, 18, 138, 242, 203, 174, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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