Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36748ae52397237571b5af3f32e834299ebec1db1a37f15767e3e00addec023c

Tx prefix hash: 55ed83aadd18b77d360d6a2a48139f4484287383ac42ebef0b4e84a5854360b8
Tx public key: 1ccc64ce3f0eef024ca21a99e3510c450d76420e22ee65022b21e425f84e06b3
Timestamp: 1637775741 Timestamp [UCT]: 2021-11-24 17:42:21 Age [y:d:h:m:s]: 02:176:05:11:41
Block: 381256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643741 RingCT/type: yes/0
Extra: 011ccc64ce3f0eef024ca21a99e3510c450d76420e22ee65022b21e425f84e06b302110000000a1cab2639000000000000000000

1 output(s) for total of 33.476572319000 dcy

stealth address amount amount idx
00: 952b0e1ffc5934c7f719bf1df892b3fdb7bfd7bd5f239e2b4a3640c3cef889cf 33.476572319000 770262 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": 381266, "vin": [ { "gen": { "height": 381256 } } ], "vout": [ { "amount": 33476572319, "target": { "key": "952b0e1ffc5934c7f719bf1df892b3fdb7bfd7bd5f239e2b4a3640c3cef889cf" } } ], "extra": [ 1, 28, 204, 100, 206, 63, 14, 239, 2, 76, 162, 26, 153, 227, 81, 12, 69, 13, 118, 66, 14, 34, 238, 101, 2, 43, 33, 228, 37, 248, 78, 6, 179, 2, 17, 0, 0, 0, 10, 28, 171, 38, 57, 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