Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fcf216464262c8ff7120f7e5ce18d3f7080832f232bc7e70dcb9c47c80e0ea1

Tx prefix hash: 276ec95e991696140220d857e77f18ece37a0731e27cf24df4be799e90d2b784
Tx public key: da3a4cdcbe93294a1595d6954e73b3fa60f2f5c594fe9a6c1f73bbf2ceb1aa4a
Timestamp: 1711769831 Timestamp [UCT]: 2024-03-30 03:37:11 Age [y:d:h:m:s]: 01:079:04:04:01
Block: 989343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317460 RingCT/type: yes/0
Extra: 01da3a4cdcbe93294a1595d6954e73b3fa60f2f5c594fe9a6c1f73bbf2ceb1aa4a02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b86a6fd51e2782d97c86e5ac7d69c5677b62a4fae33a270b355f6a2de6d571ac 0.600000000000 1449640 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": 989353, "vin": [ { "gen": { "height": 989343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b86a6fd51e2782d97c86e5ac7d69c5677b62a4fae33a270b355f6a2de6d571ac" } } ], "extra": [ 1, 218, 58, 76, 220, 190, 147, 41, 74, 21, 149, 214, 149, 78, 115, 179, 250, 96, 242, 245, 197, 148, 254, 154, 108, 31, 115, 187, 242, 206, 177, 170, 74, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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