Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcdee61ebf87928a33e7f2398d415e95564cd9c00e76f3574f3ef6c9431c6fc2

Tx prefix hash: 372c976d7c925653e40427b1b3cc59b4501f401ba896878797ebf35f16bd13d1
Tx public key: ddf899da505debe202af9d4cfbfddec2a45a2aee3ed88a1cecc799313a1a57bd
Timestamp: 1672572979 Timestamp [UCT]: 2023-01-01 11:36:19 Age [y:d:h:m:s]: 02:099:07:38:14
Block: 665226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592664 RingCT/type: yes/0
Extra: 01ddf899da505debe202af9d4cfbfddec2a45a2aee3ed88a1cecc799313a1a57bd02110000000552542ceb000000000000000000

1 output(s) for total of 3.835571454000 dcy

stealth address amount amount idx
00: 36287e5d7aed206d249ae9e3e9050b5832dd3a489f0081e9ea2eaa54d0885555 3.835571454000 1106247 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": 665236, "vin": [ { "gen": { "height": 665226 } } ], "vout": [ { "amount": 3835571454, "target": { "key": "36287e5d7aed206d249ae9e3e9050b5832dd3a489f0081e9ea2eaa54d0885555" } } ], "extra": [ 1, 221, 248, 153, 218, 80, 93, 235, 226, 2, 175, 157, 76, 251, 253, 222, 194, 164, 90, 42, 238, 62, 216, 138, 28, 236, 199, 153, 49, 58, 26, 87, 189, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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