Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b86b6272d832daa69323968995900c5190e4932402ddb9c16143eb083fe9acfb

Tx prefix hash: 3a5b9448f995f6469a8da21b81d817a2a5f315a8a2e525a4c8b8def03284d19d
Tx public key: 880ca4d841ec5c351ae7bffe421fea2645fb4d2ec0a1bb97142ae977920d6204
Timestamp: 1617471344 Timestamp [UCT]: 2021-04-03 17:35:44 Age [y:d:h:m:s]: 03:216:20:16:08
Block: 232542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914584 RingCT/type: yes/0
Extra: 01880ca4d841ec5c351ae7bffe421fea2645fb4d2ec0a1bb97142ae977920d620402110000005da1bbccc7000000000000000000

1 output(s) for total of 104.109988643000 dcy

stealth address amount amount idx
00: 6deaddda6123c8c249a4d2ba99dfc0c67464231bd03efee03f8c9db6a87e033a 104.109988643000 483134 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": 232552, "vin": [ { "gen": { "height": 232542 } } ], "vout": [ { "amount": 104109988643, "target": { "key": "6deaddda6123c8c249a4d2ba99dfc0c67464231bd03efee03f8c9db6a87e033a" } } ], "extra": [ 1, 136, 12, 164, 216, 65, 236, 92, 53, 26, 231, 191, 254, 66, 31, 234, 38, 69, 251, 77, 46, 192, 161, 187, 151, 20, 42, 233, 119, 146, 13, 98, 4, 2, 17, 0, 0, 0, 93, 161, 187, 204, 199, 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