Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854025854d19f2df8d0111505b6ec2bca46861592968c5048644e40fa8c27075

Tx prefix hash: be1a5f8fd7bdf20d4f443051aab8f645677a13937ac5dc79dd8511019598190f
Tx public key: fec0a9f7459a85733da298f5f95d210719cf519e78c8a8b71ab7274d72b24bef
Timestamp: 1578867738 Timestamp [UCT]: 2020-01-12 22:22:18 Age [y:d:h:m:s]: 05:028:11:42:05
Block: 44223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170492 RingCT/type: yes/0
Extra: 01fec0a9f7459a85733da298f5f95d210719cf519e78c8a8b71ab7274d72b24bef0211000000034943cd9f000000000000000000

1 output(s) for total of 438.049813410000 dcy

stealth address amount amount idx
00: ad3d8e6d623ddfb76fb35dd310db8178940f36ae4fcbf3ae7c6a84c6d676bc25 438.049813410000 80401 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": 44233, "vin": [ { "gen": { "height": 44223 } } ], "vout": [ { "amount": 438049813410, "target": { "key": "ad3d8e6d623ddfb76fb35dd310db8178940f36ae4fcbf3ae7c6a84c6d676bc25" } } ], "extra": [ 1, 254, 192, 169, 247, 69, 154, 133, 115, 61, 162, 152, 245, 249, 93, 33, 7, 25, 207, 81, 158, 120, 200, 168, 183, 26, 183, 39, 77, 114, 178, 75, 239, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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