Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61be573023f3dad092cf3f9f534231c4769ba7533fe3e9ce0e0760f341bbbe22

Tx prefix hash: 46dd69980c1a52d0a5eab1be6a84f66bd232afed200ee03c7cd07fd1f900aa93
Tx public key: a6c776d175cbd90ef8113f015de595b5cc35a3ebed2c638a9ee6428b5189b414
Timestamp: 1577908273 Timestamp [UCT]: 2020-01-01 19:51:13 Age [y:d:h:m:s]: 05:001:16:30:24
Block: 36572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151299 RingCT/type: yes/0
Extra: 01a6c776d175cbd90ef8113f015de595b5cc35a3ebed2c638a9ee6428b5189b4140211000000c878873133000000000000000000

1 output(s) for total of 464.333596733000 dcy

stealth address amount amount idx
00: 754e5b1f45657291f78fb7d233af65f6e47ead5c7cceb33ce0d88680c7794c4a 464.333596733000 61981 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": 36582, "vin": [ { "gen": { "height": 36572 } } ], "vout": [ { "amount": 464333596733, "target": { "key": "754e5b1f45657291f78fb7d233af65f6e47ead5c7cceb33ce0d88680c7794c4a" } } ], "extra": [ 1, 166, 199, 118, 209, 117, 203, 217, 14, 248, 17, 63, 1, 93, 229, 149, 181, 204, 53, 163, 235, 237, 44, 99, 138, 158, 230, 66, 139, 81, 137, 180, 20, 2, 17, 0, 0, 0, 200, 120, 135, 49, 51, 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