Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352923e7521c6990c95a32477d6631189d9783c9315294c05824a0c5a6bdc854

Tx prefix hash: 2b086991ebf7df073ee0c38594850e14b817a0fa297651782bc26ca9a550ddc8
Tx public key: 557d28df70df8977ab1a17f939fc2e372c4024fed7df720ac8a7f5c91cab1c45
Timestamp: 1710298145 Timestamp [UCT]: 2024-03-13 02:49:05 Age [y:d:h:m:s]: 01:021:06:13:30
Block: 977133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276167 RingCT/type: yes/0
Extra: 01557d28df70df8977ab1a17f939fc2e372c4024fed7df720ac8a7f5c91cab1c450211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf655dc9a6ef1fc3cdfca4ad8bf1d77ad566d800789f6656cf18b04dfbadb99 0.600000000000 1437134 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": 977143, "vin": [ { "gen": { "height": 977133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf655dc9a6ef1fc3cdfca4ad8bf1d77ad566d800789f6656cf18b04dfbadb99" } } ], "extra": [ 1, 85, 125, 40, 223, 112, 223, 137, 119, 171, 26, 23, 249, 57, 252, 46, 55, 44, 64, 36, 254, 215, 223, 114, 10, 200, 167, 245, 201, 28, 171, 28, 69, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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