Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d78487378e73069f759d4e89c7897486ed0d26ba134135a85b036d05b19071

Tx prefix hash: 63276990fb571d0d782160c99c7d4a58bd96fe74449fc35564ec1d8b89c9d7ef
Tx public key: cd61ab66fc8af93c785b6ebb86dd569d8a15ae5a0a66b0be6b4ed5deca90519f
Timestamp: 1673444092 Timestamp [UCT]: 2023-01-11 13:34:52 Age [y:d:h:m:s]: 02:004:09:04:38
Block: 672446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525023 RingCT/type: yes/0
Extra: 01cd61ab66fc8af93c785b6ebb86dd569d8a15ae5a0a66b0be6b4ed5deca90519f0211000000028b7b6602000000000000000000

1 output(s) for total of 3.630054890000 dcy

stealth address amount amount idx
00: c007046eefa5e43cefb5bfd4a09f6c8abee36ebc2398d8e681b27183e170055d 3.630054890000 1113991 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": 672456, "vin": [ { "gen": { "height": 672446 } } ], "vout": [ { "amount": 3630054890, "target": { "key": "c007046eefa5e43cefb5bfd4a09f6c8abee36ebc2398d8e681b27183e170055d" } } ], "extra": [ 1, 205, 97, 171, 102, 252, 138, 249, 60, 120, 91, 110, 187, 134, 221, 86, 157, 138, 21, 174, 90, 10, 102, 176, 190, 107, 78, 213, 222, 202, 144, 81, 159, 2, 17, 0, 0, 0, 2, 139, 123, 102, 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