Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84fab6a59091b67b391f469bcbaad36bed99c1d64b9b3093b78ae3c340b33bf7

Tx prefix hash: 6b9c4c80456ab7c78435dc74464f9c7c962d311263a30a84967d41a405a57cd1
Tx public key: 47d932631515e54c0593e0084118dbe1f2d295ebbc18fb0d4e8fe4f83508dff0
Timestamp: 1718259256 Timestamp [UCT]: 2024-06-13 06:14:16 Age [y:d:h:m:s]: 00:197:16:37:36
Block: 1043127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141465 RingCT/type: yes/0
Extra: 0147d932631515e54c0593e0084118dbe1f2d295ebbc18fb0d4e8fe4f83508dff00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 858343a94675fb533f48f3bb7362f8bd66ca59a8ee8ec610e5ed76a791d2cd36 0.600000000000 1512204 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": 1043137, "vin": [ { "gen": { "height": 1043127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "858343a94675fb533f48f3bb7362f8bd66ca59a8ee8ec610e5ed76a791d2cd36" } } ], "extra": [ 1, 71, 217, 50, 99, 21, 21, 229, 76, 5, 147, 224, 8, 65, 24, 219, 225, 242, 210, 149, 235, 188, 24, 251, 13, 78, 143, 228, 248, 53, 8, 223, 240, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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