Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a230df2d4bc9090856aecb6437ee9e17a030ce0ed746f746b883f72abff63c5a

Tx prefix hash: 066a7e9f10a85c9dd4e9f472f652dd12389e2dd32142baf50e21e9ba87c2b7db
Tx public key: 8d725a389e1ca7e278bf09a7bbf5fef9319558bcb18f4dfc21e615d385e255b6
Timestamp: 1708328568 Timestamp [UCT]: 2024-02-19 07:42:48 Age [y:d:h:m:s]: 01:096:09:05:08
Block: 960794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329957 RingCT/type: yes/0
Extra: 018d725a389e1ca7e278bf09a7bbf5fef9319558bcb18f4dfc21e615d385e255b602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e741ee9671092c7023c7a3e82b79cb05220b14cfcf3dc654db638cfa2e1e17 0.600000000000 1420381 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": 960804, "vin": [ { "gen": { "height": 960794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e741ee9671092c7023c7a3e82b79cb05220b14cfcf3dc654db638cfa2e1e17" } } ], "extra": [ 1, 141, 114, 90, 56, 158, 28, 167, 226, 120, 191, 9, 167, 187, 245, 254, 249, 49, 149, 88, 188, 177, 143, 77, 252, 33, 230, 21, 211, 133, 226, 85, 182, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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