Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e3074128b1436604b4387bbe279f023938343e5d0cd74dd98cedca6e938017b

Tx prefix hash: 25d85bbd26007a0a3a616bc2453f5a81d0c0162d0dfa608da1e787e6e353b720
Tx public key: 49a482600dfd90f445a992f48655e4cc12c2e8e5227a0180da1df1731f2679a7
Timestamp: 1722231441 Timestamp [UCT]: 2024-07-29 05:37:21 Age [y:d:h:m:s]: 00:245:14:24:07
Block: 1076053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175436 RingCT/type: yes/0
Extra: 0149a482600dfd90f445a992f48655e4cc12c2e8e5227a0180da1df1731f2679a702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f592dbfa5c6a861c801dfd3a8baf285bd1d862b4d9eca1acc0bf7527b46dff03 0.600000000000 1548588 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": 1076063, "vin": [ { "gen": { "height": 1076053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f592dbfa5c6a861c801dfd3a8baf285bd1d862b4d9eca1acc0bf7527b46dff03" } } ], "extra": [ 1, 73, 164, 130, 96, 13, 253, 144, 244, 69, 169, 146, 244, 134, 85, 228, 204, 18, 194, 232, 229, 34, 122, 1, 128, 218, 29, 241, 115, 31, 38, 121, 167, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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