Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b8cbc30f00d32f6a1798c73e1e4cd29487a92bdccbbfcf1bf568cdfa583cab

Tx prefix hash: f58aa4fcb9d31c82059b517ccbf1657a3015aacb1f1982006e1188ec41b32331
Tx public key: 1f481d3ec30f11d62d86a2e20672aa002dc2ea458dfd0ef221f42a93931ded0f
Timestamp: 1631427219 Timestamp [UCT]: 2021-09-12 06:13:39 Age [y:d:h:m:s]: 04:050:00:56:22
Block: 332113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069658 RingCT/type: yes/0
Extra: 011f481d3ec30f11d62d86a2e20672aa002dc2ea458dfd0ef221f42a93931ded0f02110000001afdc024ec000000000000000000

1 output(s) for total of 48.704849734000 dcy

stealth address amount amount idx
00: 9c8a5c40a2a59bd62d48c4a0f3bd1e8605e3c327bbe67fbef4dc59673d42bc4d 48.704849734000 685976 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": 332123, "vin": [ { "gen": { "height": 332113 } } ], "vout": [ { "amount": 48704849734, "target": { "key": "9c8a5c40a2a59bd62d48c4a0f3bd1e8605e3c327bbe67fbef4dc59673d42bc4d" } } ], "extra": [ 1, 31, 72, 29, 62, 195, 15, 17, 214, 45, 134, 162, 226, 6, 114, 170, 0, 45, 194, 234, 69, 141, 253, 14, 242, 33, 244, 42, 147, 147, 29, 237, 15, 2, 17, 0, 0, 0, 26, 253, 192, 36, 236, 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