Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 699cf28980ed74eed33f34eca71ade51f18ebcf2fcecef8aed0f676a7769c467

Tx prefix hash: 8594803c23ee0c2a9653dc2beb06a9398d92a9af50aa61ca9cf2d723e3cffc16
Tx public key: fd3d6076d256af4b47aaab8d7e859c01b27bf9d97288c6e2153c36df0fad58d4
Timestamp: 1607647176 Timestamp [UCT]: 2020-12-11 00:39:36 Age [y:d:h:m:s]: 03:330:23:04:28
Block: 159774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 987635 RingCT/type: yes/0
Extra: 01fd3d6076d256af4b47aaab8d7e859c01b27bf9d97288c6e2153c36df0fad58d4021100000010c6b81c9d000000000000000000

1 output(s) for total of 181.391980071000 dcy

stealth address amount amount idx
00: f27599e903400493109fa6cd7b809afae7de0d745cdaac34485e326b40034cf9 181.391980071000 280145 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": 159784, "vin": [ { "gen": { "height": 159774 } } ], "vout": [ { "amount": 181391980071, "target": { "key": "f27599e903400493109fa6cd7b809afae7de0d745cdaac34485e326b40034cf9" } } ], "extra": [ 1, 253, 61, 96, 118, 210, 86, 175, 75, 71, 170, 171, 141, 126, 133, 156, 1, 178, 123, 249, 217, 114, 136, 198, 226, 21, 60, 54, 223, 15, 173, 88, 212, 2, 17, 0, 0, 0, 16, 198, 184, 28, 157, 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