Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7ee50d2836d56aefe5530cea3b6865dfbc2a84e94bdec3b3c26d34be1d70dd

Tx prefix hash: 813f2298b071473229afa714e4a333d78931d8db7a85426e671847b70448166b
Tx public key: 5f00ce88f2c28105e8b012a794f27042732515836a845cdf37bff68609f7e624
Timestamp: 1598187427 Timestamp [UCT]: 2020-08-23 12:57:07 Age [y:d:h:m:s]: 04:263:08:15:59
Block: 129160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152409 RingCT/type: yes/0
Extra: 015f00ce88f2c28105e8b012a794f27042732515836a845cdf37bff68609f7e6240211000000124ac5aa02000000000000000000

1 output(s) for total of 229.107878107000 dcy

stealth address amount amount idx
00: 13848feac8db9b3a02ea14b8209509d8b9a40af42e4fb7ac0c9227788db5ed47 229.107878107000 216690 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": 129170, "vin": [ { "gen": { "height": 129160 } } ], "vout": [ { "amount": 229107878107, "target": { "key": "13848feac8db9b3a02ea14b8209509d8b9a40af42e4fb7ac0c9227788db5ed47" } } ], "extra": [ 1, 95, 0, 206, 136, 242, 194, 129, 5, 232, 176, 18, 167, 148, 242, 112, 66, 115, 37, 21, 131, 106, 132, 92, 223, 55, 191, 246, 134, 9, 247, 230, 36, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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