Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5610b3599497cf0c6a543be47ddb38fdd1934506ea2ee8b16c38a64d2e70c5d3

Tx prefix hash: aefc87773918230afc5d53a1f95972f9b118f621a15aeccb762401df1af5002a
Tx public key: d3e6069ae97b49417f688cc30451b589165e06aaa2d2a8779c0e104f60f56a4d
Timestamp: 1748524933 Timestamp [UCT]: 2025-05-29 13:22:13 Age [y:d:h:m:s]: 00:131:18:11:37
Block: 1293508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91791 RingCT/type: yes/0
Extra: 01d3e6069ae97b49417f688cc30451b589165e06aaa2d2a8779c0e104f60f56a4d02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd7bb025d0e2dd70ca335c7956cfd344c2f40427973f636fe1cde01d0e465c07 0.600000000000 1780981 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": 1293518, "vin": [ { "gen": { "height": 1293508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd7bb025d0e2dd70ca335c7956cfd344c2f40427973f636fe1cde01d0e465c07" } } ], "extra": [ 1, 211, 230, 6, 154, 233, 123, 73, 65, 127, 104, 140, 195, 4, 81, 181, 137, 22, 94, 6, 170, 162, 210, 168, 119, 156, 14, 16, 79, 96, 245, 106, 77, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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