Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b97e12eddaf00532570fcf3d9032be237665c4e671156d513581f83ac54be84

Tx prefix hash: fee7d3674f441ad6681f24b4f530030f89074f214fc988c75cfca64359c921d9
Tx public key: 2d3a0a61ffe8ff72b8fff6c8e6c67b26dae01be17aa1639e8dbffcd881e32ff8
Timestamp: 1583527408 Timestamp [UCT]: 2020-03-06 20:43:28 Age [y:d:h:m:s]: 04:296:14:46:35
Block: 77513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106752 RingCT/type: yes/0
Extra: 012d3a0a61ffe8ff72b8fff6c8e6c67b26dae01be17aa1639e8dbffcd881e32ff80211000000088a2ee0d9000000000000000000

1 output(s) for total of 339.756713800000 dcy

stealth address amount amount idx
00: db0fcb3a691cd7e6e5200b053355137bcc24f1bd4857eb20f92ead317ca1641c 339.756713800000 142654 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": 77523, "vin": [ { "gen": { "height": 77513 } } ], "vout": [ { "amount": 339756713800, "target": { "key": "db0fcb3a691cd7e6e5200b053355137bcc24f1bd4857eb20f92ead317ca1641c" } } ], "extra": [ 1, 45, 58, 10, 97, 255, 232, 255, 114, 184, 255, 246, 200, 230, 198, 123, 38, 218, 224, 27, 225, 122, 161, 99, 158, 141, 191, 252, 216, 129, 227, 47, 248, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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