Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d0572f8af988d4c91d2e0f05bb6af394082b977f57ac90fa34b1439ef1e520

Tx prefix hash: 44ba9487cf44265ef724c5ea9e47aaac427c02902b642f3fd219c8ca03775817
Tx public key: 8759c617bce5404084aa8282c3e53ce077002b65448aa5f2a795c51739fc342f
Timestamp: 1709518784 Timestamp [UCT]: 2024-03-04 02:19:44 Age [y:d:h:m:s]: 01:106:23:53:10
Block: 970669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337372 RingCT/type: yes/0
Extra: 018759c617bce5404084aa8282c3e53ce077002b65448aa5f2a795c51739fc342f02110000001459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf768bfc2fa2c4d93d3a39d053bf98d8522fef5c47e5233d3b7e0802ff42207e 0.600000000000 1430528 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": 970679, "vin": [ { "gen": { "height": 970669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf768bfc2fa2c4d93d3a39d053bf98d8522fef5c47e5233d3b7e0802ff42207e" } } ], "extra": [ 1, 135, 89, 198, 23, 188, 229, 64, 64, 132, 170, 130, 130, 195, 229, 60, 224, 119, 0, 43, 101, 68, 138, 165, 242, 167, 149, 197, 23, 57, 252, 52, 47, 2, 17, 0, 0, 0, 20, 89, 218, 211, 245, 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