Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7fbe5efa93520c7eaa63b9438cd0fc14e50aa5d73b3a70d27aa33c1b1d8e92b

Tx prefix hash: de5b99e149f77e65c293a97e62daed245f26bb7c943d4ae67563c5e41a963a2b
Tx public key: ea17118e0eb78f3be0abcbb68c4a65e2b16ee59503c1c6f2f594588069eafe2a
Timestamp: 1724899930 Timestamp [UCT]: 2024-08-29 02:52:10 Age [y:d:h:m:s]: 00:235:23:39:09
Block: 1098170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168526 RingCT/type: yes/0
Extra: 01ea17118e0eb78f3be0abcbb68c4a65e2b16ee59503c1c6f2f594588069eafe2a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3153ed609ce60aa7c5aaabc9bb04324a5eb1edbb44013a4715a8084cc80adb6 0.600000000000 1573797 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": 1098180, "vin": [ { "gen": { "height": 1098170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3153ed609ce60aa7c5aaabc9bb04324a5eb1edbb44013a4715a8084cc80adb6" } } ], "extra": [ 1, 234, 23, 17, 142, 14, 183, 143, 59, 224, 171, 203, 182, 140, 74, 101, 226, 177, 110, 229, 149, 3, 193, 198, 242, 245, 148, 88, 128, 105, 234, 254, 42, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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