Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78ad66208346de1c107832e56f97742218e09344d1a1f7af6c99d68db7f0e731

Tx prefix hash: cd028d78eaf8fc7ca14e895075ff54f44176626a7902f65311c3efc3ac347a24
Tx public key: 63c7ea4c4d6d373c43a6775dbd03df0434d7f7f3f53823e9448aaa7975411f5a
Timestamp: 1735305893 Timestamp [UCT]: 2024-12-27 13:24:53 Age [y:d:h:m:s]: 00:110:13:50:32
Block: 1184317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78832 RingCT/type: yes/0
Extra: 0163c7ea4c4d6d373c43a6775dbd03df0434d7f7f3f53823e9448aaa7975411f5a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a74369a9b8ddada45aed2e8358dea3828bc24fa23ccedcba21ff86f375be945 0.600000000000 1670774 of 15

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": 1184327, "vin": [ { "gen": { "height": 1184317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a74369a9b8ddada45aed2e8358dea3828bc24fa23ccedcba21ff86f375be945" } } ], "extra": [ 1, 99, 199, 234, 76, 77, 109, 55, 60, 67, 166, 119, 93, 189, 3, 223, 4, 52, 215, 247, 243, 245, 56, 35, 233, 68, 138, 170, 121, 117, 65, 31, 90, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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