Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d780e6957665e28911f406c24a64d5d03c078f26c1fc1c7cf93120bc5241e2f0

Tx prefix hash: f4954cd7894d83b755a63bb09132cc66fcf1eb7bad03e80e60c255ac4a47f7ff
Tx public key: a736a14be8b257e8f248ae3b4cd783695eae5aa211c5bc3eb849b02db3f72e31
Timestamp: 1711739238 Timestamp [UCT]: 2024-03-29 19:07:18 Age [y:d:h:m:s]: 00:361:07:44:53
Block: 989096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258291 RingCT/type: yes/0
Extra: 01a736a14be8b257e8f248ae3b4cd783695eae5aa211c5bc3eb849b02db3f72e3102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166bc59fa044322d6d8feb3f481751ec2d6215af73a9fc40ab95b981acad1e87 0.600000000000 1449391 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": 989106, "vin": [ { "gen": { "height": 989096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166bc59fa044322d6d8feb3f481751ec2d6215af73a9fc40ab95b981acad1e87" } } ], "extra": [ 1, 167, 54, 161, 75, 232, 178, 87, 232, 242, 72, 174, 59, 76, 215, 131, 105, 94, 174, 90, 162, 17, 197, 188, 62, 184, 73, 176, 45, 179, 247, 46, 49, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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