Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e0b2241507c6eca9e6806c17f423f067f36e29fef06c4d51dabb879ba3671fc

Tx prefix hash: 5ab0794343d513ee24418dd81aa8eb1ba02e0db8f79c65300cba3695d060e195
Tx public key: b2bbc98c412091b3025d1c2de8ea4f3a343a166b1cf122e1bff8ee78aa23323d
Timestamp: 1702461689 Timestamp [UCT]: 2023-12-13 10:01:29 Age [y:d:h:m:s]: 01:193:14:57:06
Block: 912174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399304 RingCT/type: yes/0
Extra: 01b2bbc98c412091b3025d1c2de8ea4f3a343a166b1cf122e1bff8ee78aa23323d02110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7422d087e7b0f68e07871567214b8db359a76bc94282e36e62483716c5bbe887 0.600000000000 1369396 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": 912184, "vin": [ { "gen": { "height": 912174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7422d087e7b0f68e07871567214b8db359a76bc94282e36e62483716c5bbe887" } } ], "extra": [ 1, 178, 187, 201, 140, 65, 32, 145, 179, 2, 93, 28, 45, 232, 234, 79, 58, 52, 58, 22, 107, 28, 241, 34, 225, 191, 248, 238, 120, 170, 35, 50, 61, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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