Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03f13c26e342a4551eec1c2840df11b900d4c41796473287cff8b5ecfa1b939

Tx prefix hash: 995d72266dddf975935367de2fcaf8f36d547f3df3e6900d8c593131f5b039a1
Tx public key: 5db025b08ad88d4a3ef57a67ddb4d5a9b2cfa245a33f93a28e906e5d42aae18e
Timestamp: 1705532243 Timestamp [UCT]: 2024-01-17 22:57:23 Age [y:d:h:m:s]: 01:079:07:54:24
Block: 937587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317796 RingCT/type: yes/0
Extra: 015db025b08ad88d4a3ef57a67ddb4d5a9b2cfa245a33f93a28e906e5d42aae18e0211000000227a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44a1918b7d4b0ef1d461e84c9a056aa11a44e10d102757130792ea4a3eaf68bf 0.600000000000 1395647 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": 937597, "vin": [ { "gen": { "height": 937587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44a1918b7d4b0ef1d461e84c9a056aa11a44e10d102757130792ea4a3eaf68bf" } } ], "extra": [ 1, 93, 176, 37, 176, 138, 216, 141, 74, 62, 245, 122, 103, 221, 180, 213, 169, 178, 207, 162, 69, 163, 63, 147, 162, 142, 144, 110, 93, 66, 170, 225, 142, 2, 17, 0, 0, 0, 34, 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