Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a98643c80c6b603a112b2241e78307016cdebc239f94a86646999d938055aea

Tx prefix hash: 3d86d5b8568a459514d104cb912bf5167e3fd4cf1c9f876a37fb54702d95e86e
Tx public key: bf3701877014c9b1a4dd278b47e4708269a9e71ce2446f9230f80790accc5eb8
Timestamp: 1735347609 Timestamp [UCT]: 2024-12-28 01:00:09 Age [y:d:h:m:s]: 00:090:02:47:23
Block: 1184654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64197 RingCT/type: yes/0
Extra: 01bf3701877014c9b1a4dd278b47e4708269a9e71ce2446f9230f80790accc5eb8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ed5a9076eb68a241b878a7d9ff90ce6e8fee7acf1a9da661ce722fe4e7f29b9 0.600000000000 1671113 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": 1184664, "vin": [ { "gen": { "height": 1184654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ed5a9076eb68a241b878a7d9ff90ce6e8fee7acf1a9da661ce722fe4e7f29b9" } } ], "extra": [ 1, 191, 55, 1, 135, 112, 20, 201, 177, 164, 221, 39, 139, 71, 228, 112, 130, 105, 169, 231, 28, 226, 68, 111, 146, 48, 248, 7, 144, 172, 204, 94, 184, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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