Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c01774681cc25217edbcc43a454227847bd95b0b72fc0e8a928a1fe89f0ef2

Tx prefix hash: de677141fbf20da8b7ef5bf4ecafd30d3397bdefa2c2a74600446628ae9f67b7
Tx public key: 1a16f21fb507c3f5b81923c383a715cc3ef4564193e288899458fee69f138c52
Timestamp: 1617072063 Timestamp [UCT]: 2021-03-30 02:41:03 Age [y:d:h:m:s]: 03:232:14:59:36
Block: 229408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925696 RingCT/type: yes/0
Extra: 011a16f21fb507c3f5b81923c383a715cc3ef4564193e288899458fee69f138c5202110000003f7071732b000000000000000000

1 output(s) for total of 106.631161733000 dcy

stealth address amount amount idx
00: 1fcc78c60f9a9f7c5fc4f7d004caf81e0cde256ce8a947903eceab3d2dd70ec2 106.631161733000 475984 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": 229418, "vin": [ { "gen": { "height": 229408 } } ], "vout": [ { "amount": 106631161733, "target": { "key": "1fcc78c60f9a9f7c5fc4f7d004caf81e0cde256ce8a947903eceab3d2dd70ec2" } } ], "extra": [ 1, 26, 22, 242, 31, 181, 7, 195, 245, 184, 25, 35, 195, 131, 167, 21, 204, 62, 244, 86, 65, 147, 226, 136, 137, 148, 88, 254, 230, 159, 19, 140, 82, 2, 17, 0, 0, 0, 63, 112, 113, 115, 43, 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