Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b1988eabbe38a8d1e643db20ccf1ea3d5e6e15d773a736f3df69b87fa36fa6

Tx prefix hash: fc3719320844e8b60c0093321d813ff80f7792c888f22fbc66007640ec069e5d
Tx public key: 0c8834dc0472e938789dab31e5b3f59b15c8f2938ad38a9038a722744585daef
Timestamp: 1679781479 Timestamp [UCT]: 2023-03-25 21:57:59 Age [y:d:h:m:s]: 02:011:21:45:55
Block: 725027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530024 RingCT/type: yes/0
Extra: 010c8834dc0472e938789dab31e5b3f59b15c8f2938ad38a9038a722744585daef021100000004b3164c24000000000000000000

1 output(s) for total of 2.430437473000 dcy

stealth address amount amount idx
00: 9fefcf842a7db059cef8964cb4ae1caf0c507b73e87c01fc6244f332e46c80f4 2.430437473000 1170102 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": 725037, "vin": [ { "gen": { "height": 725027 } } ], "vout": [ { "amount": 2430437473, "target": { "key": "9fefcf842a7db059cef8964cb4ae1caf0c507b73e87c01fc6244f332e46c80f4" } } ], "extra": [ 1, 12, 136, 52, 220, 4, 114, 233, 56, 120, 157, 171, 49, 229, 179, 245, 155, 21, 200, 242, 147, 138, 211, 138, 144, 56, 167, 34, 116, 69, 133, 218, 239, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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