Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fcaefa10ac0e1911f8773c8d6925d158264971f86c6e8883bb99aa69800ea4a

Tx prefix hash: 493ae81f8e57b461496ffbbec635cc9f5d3a164dc457cf8ff499950229cfb7be
Tx public key: 23fbb43ab6c1470e0836fba7cb9aa4406d44983d9df95164f5c4c5fc110fb61e
Timestamp: 1704585187 Timestamp [UCT]: 2024-01-06 23:53:07 Age [y:d:h:m:s]: 01:317:16:47:26
Block: 929739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485910 RingCT/type: yes/0
Extra: 0123fbb43ab6c1470e0836fba7cb9aa4406d44983d9df95164f5c4c5fc110fb61e02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04ca007d8bd0e57b009ccc41d710a689e7114ed333ee316cfcc95c15b73e30b2 0.600000000000 1387615 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": 929749, "vin": [ { "gen": { "height": 929739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04ca007d8bd0e57b009ccc41d710a689e7114ed333ee316cfcc95c15b73e30b2" } } ], "extra": [ 1, 35, 251, 180, 58, 182, 193, 71, 14, 8, 54, 251, 167, 203, 154, 164, 64, 109, 68, 152, 61, 157, 249, 81, 100, 245, 196, 197, 252, 17, 15, 182, 30, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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